If you want proof, the data is available in the .bin outputs LFS creates. My VHPA has a reader for the .bin files (the format was basically a request I made to Scawen so I could analyse the cars as thoroughly as possible).
I would avoid mixing and matching graphics cards brands. Must be easier on the system to only have one graphics driver running.
Your biggest problem is, if these specifications are correct, is your motherboard. If your other PCIe slots are only 1x, then the secondary graphics card probably won't run in 3D mode. So you'll get triple desktop, but not triple screen gaming. I had to upgrade my motherboard to get two 8x slots, before my secondary card would run in 3D mode.
People editing the map is already starting to piss me off. I've had to put the description text back 4 times already, and somebody deleted my marker. :|
I don't think this is due to the devs wanting to make everyone sad and neglect rallycross, I just don't think it was covered in the laser scanning data, and they didn't want to have the rest of it real and then make that part up.
Now you've just reduced your magical powers of administratorship down to click buttons some other code monkey wrote. This is indeed a sad day in the world of LFS.
As it stands, Live for Speed has many limitations that makes recreating a NASCAR sprint cup COT less than perfect. For example:
* No modelling of solid axle suspension (only independent options available)
* No modelling of ratcheting locking differentials (i.e. Detroit NoSpin)
* No modelling of axle wrap (and thus wheel hop)
* No modelling of configurable 'soft' bump stops
* No modelling of carburetted engines
* No modelling of bump or roll steer
* No support for asymmetric springs, dampers, caster angles or tyre dimensions
* No support for wedging the car (i.e. asymmetric ride heights)
* No support for adjustable roll centre height
* No support for aerodynamically deployed roof flaps
* No tyre blow outs, punctures, or modelling of inner liners
* No tyre compound that matches (and I've not found where to edit that information)
* Limited drafting and aerodynamic modelling
* Dubious tyre heat modelling
And that's just the car physics issues. Add to that track physics, lack of appropriate tracks, and none of the NASCAR rules and regulations, and you have something that couldn't get close to the proper experience.
Yep. Not a lot I can do about that, given the nature of it. Be nice if there was an "add only" mode. I'll try and keep an eye on it though. On the plus side, being open, if anyone does screw it up, anyone can fix it too (if what they did is obvious).
As the site used in the original thread was dead, I've created a public google map people can add markers too, so we can see the spread of LFS users around the world. You'll need a google account.
I have no problem what-so-ever with links to contests where a user here has an entry. I think it is only fair that the OP should have a link to the main contest page as well as his entry, and that people should listen to more than just Schuppor's entry before voting. Remember, this is a competition, you're not voting to say you like it, but voting to say you like it best.
The lateral acceleration squared plus the longitudinal accelerated squared, square rooted, gives your total (i.e. the Pythagorean theorem). So in your nice example of a tyre with a perfect traction circle (although this also applies correctly to an ellipse, but sadly real tyres are more complicated than an ellipse too), adding or 5% of lateral force capability decreases maximum longitudinal force by only 0.13%.
Likewise if a tyre were creating 0.95g braking and 0.05g cornering, the vector length (i.e. the combined total) would not be 1.0g, but 0.9513g. In fact you'd need to be cornering at 0.31g to reduce braking down to 0.95g.